A Model-Based Approach To Requirements Analysis

A major task in designing embedded systems is the systematic elaboration of functional system requirements and their integration into the environment of the complete technical system. The main challenge is to handle the versatile tasks of coordinating a definition of behavior, which is appropriate to the problem. The problem- and design-specifications of the customer related product definition have to be adjusted with and integrated into the manifold requirements of the technical system design. Accordingly, the model-based requirements analysis and system-definition presented here defines a well-structured modeling approach, which systematically aids the goal-oriented formulation and adjustment of the different stakeholder-requirements with the aid of views onto the system and descriptive specification techniques. Thus it allows a clear specification of a consistent and complete system design. The central steps of this approach are implemented in a requirements management (RM) tool prototype called AutoRAI

Interdisciplinary Requirements Analysis Using the Model-based RM Tool AUTORAID

A major task in designing embedded systems is the systematic elaboration of functional system requirements and their integration into the environment of the overall technical system. The main challenge is to handle the versatile tasks of coordinating the communication and consolidation of the various stakeholder requirements of the different involved diciplines and derive a common definition of the system behavior, which is appropriate to the problem. The problem- and customer-related product definition must be consolidated with and integrated into the manifold requirements of the functional and technical system design. Accordingly, the model-based requirements analysis and system-definition presented here defines a well-structured modeling approach, which provides a basic model of RE work products (RE Product Model) and systematically guides the goal-oriented formulation and adjustment of the different stakeholder-requirements by using functional system views and descriptive specification techniques. Thus it allows a clear specification of a consistent and complete system design. The central steps of this approach are implemented in a requirements management (RM) tool prototype called AUTORAID. 1

A Model-Based Approach To Requirements Analysis

A major task in designing systems development is the systematic elaboration of functional system requirements and their integration into the environment of the overall technical system. The main challenge is to handle the versatile tasks of coordinating the communication and consolidation of the various stakeholder requirements of the different involved diciplines and derive a common definition of the system behavior, which is appropriate to the problem. The problem- and customer-related product definition must be consolidated with and integrated into the manifold requirements of the functional and technical system design. Accordingly, the model-based requirements analysis and system-definition presented here defines a well-structured modeling approach, which provides a basic model of RE work products (RE Product Model) and systematically guides the goal-oriented formulation and adjustment of the different stakeholder-requirements by using functional system views and descriptive specification techniques. Thus it allows a clear specification of a consistent and complete system design. The central steps of this approach are implemented in a requirements management (RM) tool prototype called AUTORAID

Exploring Coordination Structures in Open Source Software Development

Coordination is difficult to achieve in a large globally distributed project setting. The problem is multiplied in open source software development projects, where most of the traditional means of coordination such as plans, system-level designs, schedules and defined process are not used. In order to maintain proper coordination in open source projects one needs to monitor the progress of the FLOSS project continuously. We propose a mechanism of display of Socio- Technical project structures that can locate the coordination problems in open source software development. Using the tool TESNA (TEchnical and Social Network Analysis) that we have developed; we cluster the software and produce a display of the different software clusters as well as the people working on its constituting software classes. We then demonstrate the technique on a sample FLOSS project that is on the brink of becoming inactive